Versions:
git-crypt is a software tool developed and published by Andrew Ayer that provides transparent file encryption within git repositories, allowing sensitive files to be stored in encrypted form while appearing as normal, readable files to authorized users working with the repository. The tool addresses a common challenge in collaborative software development, where certain files such as configuration secrets, credentials, certificates, or other confidential data must be version-controlled alongside source code but cannot be exposed to everyone with access to the repository. With git-crypt, designated files are automatically encrypted when committed and transparently decrypted when checked out by users who possess the appropriate key, so the encryption process does not interfere with ordinary git workflows such as committing, branching, diffing, or merging. Users without the key can still clone and work with the repository normally, but the protected files remain in their encrypted, unreadable form, which makes the software particularly suitable for mixed-trust environments where not every contributor should have access to all repository contents. Typical use cases include storing API keys, passwords, private keys, and other secrets in the same repository as application code, keeping infrastructure configuration secure in shared projects, and protecting sensitive assets while preserving the full benefits of git's version history and collaboration features. git-crypt falls within the security and developer tools categories, specifically serving version control users who need file-level encryption integrated directly into their existing git-based processes. The current version of the software is 0.7.0, and according to the available catalog information only one version is listed, meaning no earlier or alternative releases are documented for comparison. As a focused, single-purpose utility, git-crypt offers a practical solution for teams seeking to balance the transparency of shared version control with the confidentiality requirements of sensitive data management.
Tags: